Transactions within CO Certification process
Within the process in the CO system, 5 sub-transactions are named. For two of the transactions, a digital message is currently being developed to exchange information in a standardized manner (T1.0 and T2.0).
| CO Certification | Digital message | |
|---|---|---|
| Commissioning notification | ||
| T1.0 | Commissioning notification of gas combustion plant for CO certification | yes |
| T1.1 | Commissioning request message | no |
| T1.2 | Detail message commissioning gas combustion plant for CO certification | no |
| Unsafe situation | ||
| T2.0 | Message of unsafe situation, (near) CO cases | yes |
| T2.1 | Message of violation of building regulations (unsafe situation) to competent authority | no |
Figure: Overview transactions
Two processes can be distinguished, Namely
Process -> Notification unsafe situation
Process -> Commissioning device
While these two messages have a connection within the CO system, in practice they are actually separate.
Example 1:
Engineer arrives on site and observes an unsafe situation.
Example 2:
Engineer arrives on site, repairs and reports plant in operation.
T1.0 - Transaction Commissioning
It is prescribed that an installation company report completed work and commissioning to the CB where it is certified. In this way, the CB can perform spot checks on the company's work. The figure shows schematically how this process works. In this case, the report can also be made available to the housing corporation by the commissioning company. In this way, the data is used in two places, after which it can be fed back to one or more residents.
Figure: Transaction Commissioning
T2.0 - Transaction Unsafe Situation
The transaction describes a report of an unsafe situation that occurred during the commissioning of an installation.
Figure: Transaction Unsafe Situation
Additional Information CO Certification
InstructionNumber field
The field <InstructionNumber> is mandatory in both transactions. And it is the instruction number obtained to do the Commissioning or resolve an UnsafeSituation.
Attachment Structure Unsafe Situation
Two attachments are required to be included in the Unsafe Situation. The attachments must contain a photo before recovery and a photo after recovery. For this you use the attachment structure. Multiple before and after photos can also be included.
Relation Unsafe Situation and Commissioning
The Unsafe Situation is a technical extension of the Commissioning. This is useful when implementing both processes. Line-level additions in the Unsafe Situation are:
[2..n] Attachment
[0..1] Location
[1..1] DeviceInformation
[1..1] UnsafeSituation
Description fields
The description fields in the CommissioningNotice and UnsafeSituationNotice are multilingual. So you can include multiple languages. This process is based on the Dutch sector and the agreement is that <LanguageCode> "NL" is used.
OpenAPI
This part of the standard is accessed via OpenAPI. The information is in JSON schemas based on the DICO Data Model.
Difference in handling codelists
There are also technical DICO Messages within the Standard where codelists are placed externally. This is the case for the SALES005 XML messages within the DICO Standard. In these OpenAPI specifications, the codes are hardcoded.